Client-Side Web Service Provider

ABSTRACT

To facilitate client access to web services, a server may be configured to package or bundle a function call for a web service with associated information. This information may include parameters for the function call and/or software code that can facilitate the function call. The software code may be configured to format user input for use as parameters of the function call, to prompt the user for parameters, to control the display of the web services received in response to execution of the function call, or to otherwise facilitate use of the function call. The resulting function call package may be distributed to multiple clients.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This is a continuation of U.S. patent application Ser. No. 10/915,858, filed Aug. 11, 2004, now allowed, entitled “CLIENT-SIDE WEB SERVICE PROVIDER,” which claims priority from Provisional Application No. 60/503,523, filed Sep. 16, 2003, entitled “CLIENT-SIDE WEB SERVICE PROVIDER,” both of which are fully incorporated by reference herein.

BACKGROUND

Many different businesses maintain a presence on the Internet. Typically, this presence is in the form of a web site, although a business may also use the Internet to access information or services, or to provide information or services. Often, a business may combine a number of these uses. For example, a business may provide a web site that provides information about the business and allows users of the web site to access services that are provided by a server that is separate from the business' web site.

Conventionally, services that reside at sites other than the business' web site have been accessed by providing a link to the other site. Thus, a user might view a first web site, see a link to a service, click on the link, and be taken to the site at which the service resides. Originally, it was typical for this type of linking to be readily apparent, as the user was simply transferred to the second web site. This could be somewhat problematic, however, as it is generally desirable for the business to keep the user at its own web site in order to maximize the effect of the web site (e.g., to increase the exposure of the business or the sales made via the web site). Techniques have therefore been developed to disguise the transfer of the user to the second web site. For instance, when a user is transferred to the second web site from the first web site, the appearance of the second web site may be altered by using graphics provided by the first web site or other indicia of the first web site. It may therefore appear that the services are actually being provided by the first web site.

Another technique for providing services over the internet is referred to as “web services.” While the services described above are provided over the web (the internet), the term “web services” is typically used (and will be used herein) to refer to services that can be accessed by making a function call to a remote server and then providing the results returned by the function call to the user of the first web site. “Web services” are further described in the Web Services Interoperability Organization's Basic Profile Version 1.0, herein incorporated by reference. While this technique keeps the user at the first web site and may simplify or streamline the process of providing the requested services to the user, there are several problems associated with the use of web services that still exist.

One problem is that, while a function call for accessing the web service may be defined and available for use by potential clients, the proper syntax for the function call may not be apparent. For example, it may be clear that the function call should include a date, but the required format of the date in the function call may not be clear. Thus, a client may make the function call with the date in the format “Jan. 1, 2002”, when the date should instead be in the format “Jan. 1, 2002”. The function call may therefore fail because the web service provider cannot interpret the date.

Another problem is that the web service provider may wish to have the web service presented in a particular way. For instance, the web service provider may be a provider of traveler's checks and may wish to have trademarks associated with the traveler's checks presented to the user in connection with the means for accessing the web service for ordering traveler's checks from the provider because a particular web service is typically accessed by looking up the form of a function call corresponding to the web service and making the function call without any regard to the branding of the service. The web services provided through the function call may therefore be presented to an end user in a way that is inconsistent with the presentation desired by the provider of the web service.

SUMMARY

One or more of the problems outlined above may be solved by the various embodiments of the invention. Broadly speaking, the invention comprises systems and methods for enabling clients to access web services, wherein function calls are packaged with information and/or code that facilitates use of the function calls.

One embodiment comprises a system that includes a server, where the server is configured to provide a web service accessible through a function call. The server is configured to bundle the function call for the web service with information for facilitating use of the web service. The resulting function call package is provided to clients so that they can access the web service. The information for facilitating use of the web service may further include information for facilitating execution of the function call which may, for example, include parameters for the call or software code. The software code can be configured to format user input for use as parameters of the function call, to prompt the user for parameters, to control the display of the results received in response to execution of the function call, or to otherwise facilitate use of the function call and the corresponding web services.

Another embodiment comprises a method that includes the steps of providing a function call for accessing a web service, bundling the function call with information for facilitating use of the web service, or execution of the function call, in a function call package, and distributing the function call package.

Another embodiment comprises a software program product. The software program product contains program instructions that are configured to cause a computer to perform the method comprising the steps of providing a function call for accessing a web service, bundling the function call with information for facilitating use of the web service or execution of the function call in a function call package, and providing the function call package to a client.

In one embodiment, a function call is packaged with information corresponding to one or more of the input parameters, output parameters, or return values defined for the function call. The information may provide the actual parameters for the function call, or they may provide information to a client that enables the client to produce a syntactically correct function call for the web service. In one embodiment, the package includes code, which may be in various languages such as Java or Perl that is configured to perform some process in support of the function call. These processes may include such things as interacting with a user to obtain parameters for the function call, formatting parameter values, making the function call, formatting the results of the call, and so on. The processes may also involve some degree of management control, such as controlling the display of the web service results to include the logos of the service provider, use certain colors, fonts, etc. in the displayed results, and so on. The code may also allow a client to customize the package, within the constraints of the service provider's controls, to fit within its own display scheme. The client may also be allowed to modify the package and to distribute the modified package to its own affiliates.

Numerous additional embodiments are also possible.

The various embodiments of the invention may provide a number of advantages over the prior art. These advantages may include, for example: overcoming syntactical problems that would otherwise be encountered by a client that is aware of the substantive content of a function call parameter, but is unaware of the particular formatting that is necessary within the framework of the function call; enabling a service provider to implement management controls to ensure proper use of logos, colors, and the like; and enabling a client to modify the package to implement its own controls within the constraints of the service provider's controls and to distribute the modified package to its affiliates to allow them to access the web service in the same manner. Still other advantages will be apparent to those of skill in the art.

BRIEF DESCRIPTION OF THE DRAWINGS

Other objects and advantages of the invention may become apparent upon reading the following detailed description and upon reference to the accompanying drawings.

FIG. 1 is a diagram illustrating some of the basic components of a network system.

FIG. 2 is a diagram illustrating the components of an exemplary computer system.

FIG. 3 is a diagram illustrating the use of a link to transfer a user from a first web site to a second web site that provides desired services.

FIG. 4 is a diagram illustrating the use of a function call package at a first web site to obtain a desired service from a second web site without the user having to leave the first web site.

FIG. 5 is a diagram illustrating an embodiment of the invention in which a service provider provides a packaged function call for use in obtaining web services.

While the invention is subject to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and the accompanying detailed description. It should be understood, however, that the drawings and detailed description are not intended to limit the invention to the particular embodiment which is described. This disclosure is instead intended to cover all modifications, equivalents and alternatives falling within the scope of the present invention.

DETAILED DESCRIPTION

One or more embodiments of the invention are described below. It should be noted that these and any other embodiments described below are exemplary and are intended to be illustrative of the invention rather than limiting.

As described herein, various embodiments of the invention comprise systems and methods for enabling access to web services wherein function calls are packaged with information and/or code that facilitates use of the function calls.

One embodiment of the present invention comprises a method for providing access to web services. In this embodiment, a web service provider makes a web service available and defines a function call that can be used to request the service (to call the web service function). The web service provider then takes the function call and packages it in a manner that facilitates its use. For example, one or more of the fields of the function call may be provided, or code may be bundled with the function call to revise improperly formatted fields in the function call before the call is executed.

Another embodiment comprises a system configured to package a function call with information corresponding to one or more of the input parameters, output parameters, or return values defined for the function call. The function call may further be packaged with code in a suitable programming language configured to perform processes in support of the function call. The information packaged with the function call may provide the actual parameters for the function call, or they may provide information that enables production of a syntactically correct function call for the web service. The code packaged with the function call may facilitate preparation or execution of the function call, or may implement management control over the display or other use of the web services.

The various embodiments of the present invention are typically implemented in a network environment. The network consists of multiple devices (e.g., workstations, servers, etc.) that may be arranged in any of a variety of topologies. A preferred embodiment of the invention is implemented in an internet environment.

Referring to FIG. 1, a diagram illustrating some of the basic components of a network system is shown. As depicted in this figure, the system comprises a client 12, a network 13, and a server 16. It should be noted that the network configuration illustrated in FIG. 1 is intended to be exemplary rather than limiting. Other embodiments may employ alternative configurations. For example, there may be multiple clients and multiple servers that are interconnected by multiple individual networks. Alternatively, a client may be directly coupled to a server without an intervening network. Many such variations are possible.

Communications between client 12, and server 16 (as well as network 13) can be accomplished using electronic, optical, radio-frequency, or other signals. For example, client 12 may convert signals received from server 16 to a human understandable form and may convert input from a human understandable form to appropriate electronic, optical, radio-frequency, or other signals to be used by server 16. Similarly, when an operator is at server 16, server 16 may convert the signals to a human understandable form when sending a communication to the operator and may convert input from a human understandable form to appropriate electronic, optical, radio-frequency, or other signals to be used by client 12.

In one embodiment, each of client 12 and server 16 is implemented in a corresponding computer system. These computer systems may comprise general purpose desktop computers, laptop computers, or other types of devices capable of communicating over the networks and processing the information communicated between them. Referring to FIG. 2, a diagram illustrating the components of an exemplary computer system is shown. The computer system illustrated in this figure may be used as a platform for client 12 or server 16.

As shown in FIG. 2, computer system 20 comprises a central processing unit (“CPU”) 22, read-only memory (“ROM”) 24, random access memory (“RAM”) 26, hard disk drive (“HD”) or storage memory 28, and input/output device(s) (“I/O”) 29. I/O 29 can include a keyboard, monitor, printer, electronic pointing device (e.g., mouse, trackball, stylus, etc.), or the like.

The computer systems that provide platforms for the client and server may each have more than one CPU, ROM, RAM, HD, I/O, or other hardware components. For simplicity, the computer illustrated in FIG. 2 is depicted in as having one of each of the listed hardware components. It should be noted that FIG. 2 is a simplification of an exemplary hardware configuration. Many other alternative hardware configurations are possible and known to persons of skill in the art.

It should be noted that, in addition to being implemented in suitable computer systems, some embodiments may be implemented in software programs or code. The software code comprises instructions configured to cause a computer on which the code is executed to perform a method in accordance with the present disclosure. These software embodiments may be referred to as software program products. The software code may be embodied in any suitable computer-readable media. For instance, the software code may reside within ROM 24, RAM 26, hard disk drives 28 or other computer-readable media within a computer system. The software code may also be contained on a separable data storage device, such as a removable hard disk, or on removable computer-readable media such as a DASD array, magnetic tape, floppy diskette, optical storage device, or the like. In one embodiment, the software code may comprise lines of compiled C⁺⁺, Java, or other language code.

“Computer” and “computer system,” as used herein, are intended to include any type of data processing system capable of performing the functions described herein. “Computer-readable media,” as used herein, refers to any medium that can store program instructions that can be executed by a computer, and includes floppy disks, hard disk drives, CD-ROMs, DVD-ROMs, RAM, ROM, DASD arrays, magnetic tapes, floppy diskettes, optical storage devices and the like.

As mentioned above, businesses may wish to maintain web sites that provide a variety of services, some of which are not resident on the business' web site. These businesses may make use of remote web sites that provide the desired services. An example is illustrated in FIG. 3. Referring to FIG. 3, a web site 100 is hosted by a business operating under the name OnlineBank.com. OnlineBank.com wishes to provide its users with a convenient way to order traveler's checks. OnlineBank.com does not provide this service locally, so it provides a link 105 to a second web site 110, which is hosted by another business as TravelersChecks.com. TravelersChecks.com has a server that delivers a function through which traveler's checks can be ordered by users. After the users order traveler's checks through this web site, however, they are left at the TravelersChecks.com site instead of being transferred back to the original (OnlineBank.com) web site.

This is the traditional way in which remote services were provided. The user was actually transferred to the remote web site by clicking on the link to the services. The display that is presented to the user could be branded for OnlineBank.com, but the user was actually at the TravelersChecks.com web site. The user then had to fill out forms or otherwise transact with the remote web site as if he or she had originally gone directly to the remote site in order to obtain the desired services (e.g., ordering traveler's checks).

This type of interaction could be used to provide other services in the same manner. For example, a business might have an affiliate program. An affiliated web site (an affiliate) can present a button to a user that says, e.g., “buy this book.” The affiliate in this example corresponds to the local (i.e., OnlineBank.com). When the user clicks on the button, the user is taken to the service provider's web site. The server at the service provider's web site keeps track of where the order came from (i.e., the affiliate web site), and a commission is paid to the affiliate.

The problem with the interactions described above is that the user was removed from the context of the original web site. After the user accessed the services that were desired, the user was left at the remote web site instead of the original web site. The business operating the original web site had thus lost the user that it had originally attracted to its web site, and consequently lost the interaction, advertising potential, etc. for which the business had originally tried to attract the user to the site.

As noted above, another technique that is available for accessing remotely provided services is the web services mechanism. Web services are also sometimes referred to as application services. The term “web services” describes a standardized way of integrating Web-based applications using open standards such as XML (Extensible Markup Language), SOAP (Simple Object Access Protocol), WSDL (Web Services Description Language) and UDDI (Universal Description, Discovery and Integration), typically over an IP-protocol network such as the internet. Usually, XML is used to tag the data, SOAP is used to transfer the data, WSDL is used for describing the services available and a UDDI server is used to provide a list of the web services that are available. Web services may be used as a means for businesses to communicate with each other and with clients, or for allowing organizations to communicate data to each other without having intimate knowledge of each other's IT systems.

Unlike traditional client/server models such as a web server/web page system, web services do not provide the user with a GUI and do not require the use of browsers or HTML. Web services instead share business logic, data and processes through a programmatic interface across a network. Software applications themselves interface with each other so that users do not have to. Developers can add web services to GUIs, often through web pages or executable programs, to offer specific functionality or services to users.

Web services allow different applications from different sources to communicate with each other without time-consuming custom coding, and because all communication is in a standardized language such as XML, Web services are not tied to any one operating system or programming language. Thus, a Java application can communicate with a Perl script, a Windows application can communicate with a UNIX application, and so on.

Using the web services mechanism, a client can generate a request to a server which provides the desired service in response to the request. While there are a variety of mechanisms for remote procedure calls that are in some respects similar, web services are somewhat unique in that they do not require that the server distribute a library of information describing the web service in order to enable its use. Other mechanisms may need information regarding the procedure for determining the existence of the server-side function, the format of the procedure call (the number and types of input and out parameters, as well as return values), the manner of invoking the procedure, and the manner of receiving a response from the server. In fact, it is typically necessary, when using mechanisms other than web services, to compile such information into the client-side software. Web services do not involve programming languages, per se, at all. The discovery and invocation process is executed using XML descriptions of the data (procedure signature and parameter definitions) over commonly used transport protocols, such as HTTP.

Referring to FIG. 4, the use of web services to provide users with access to services residing on remote sites is illustrated. Web services allow the user to stay within the context of the original web site 200 (OnlineBank.com), but still access the remotely provided service by transitioning the user into a wizard 210 or similar process within the original web site. (Although shown separately in the figure, wizard 210 is a process operating within the context of web site 200.) Wizard 210 interacts with the user 220 and collects the necessary information for the desired transaction, then submits a transaction to a transaction system 230 associated with the remote web site 240 which provides the service. Transaction system 230 processes the transaction (e.g., creates the order for the traveler's checks) and typically responds to wizard 210 on original web site 200 with a confirmation. The confirmation then provides the basis for a display that is presented to user 220. It should be noted that the transaction is directed to transaction system 230, and not to web site 240 itself. Thus, while the transaction may appear in many respects to the user to be the same as the previous methods, the user never actually leaves the original web site.

Transaction system 230 may be a server. The purpose of the server is to provide a function or service, such as ordering travelers checks. There are a set of parameters that server needs to have in order to process an order for travelers checks. These parameters may include such information as the user's address, quantity of traveler's checks desired, denominations, partner credentials (to make sure that the order is coming from a partner authorized to use the system), and so on. This information may take the form of strings, integers, binary values, logical values or various other types of data. This information is used to make a function call to the server to access the function or service. In the context of web services, this function call is expressed in a way that anyone who can use web services has this function call available to them, so that they can make the function call to the server and place an order for traveler's checks.

The function call is formatted in a way that it can be used by essentially anyone. Typically, the function call is defined or formatted in web services description language, or WSDL. WSDL is used to define the parameters of the function call so that it can be made available to potential users of the service. The function call in WSDL usually has input parameters, output parameters and a return value. Each of these parameters is defined by a name and a type.

Prior to the advent of web services, the function call parameters would all be expressed in binary representations, and header files, and the like. Anybody that wanted to use the function call had to compile code that was provided by the service provider into their software in order to be able to make the function calls for the desired services. In a web services environment, it is not necessary for a potential user of the web services to obtain any code to compile into their own software. Instead, these potential users only have to have an explanation of how the function call is made. The function call can then be made in XML, possibly using SOAP.

The location of the function call for a web service can be determined by accessing a UDDI server. UDDI is a directory service. The UDDI server identifies web services that are available, who provides them, and the manner in which function calls for these Web services are made. For example, there are public UDDI servers. It is possible to browse into these servers and find different services. For instance, the UDDI server might identify a service for temperature conversion. According to the information in the UDDI server, the function call might require that a number, a type (e.g., Fahrenheit) for the temperature prior to conversion, and a type for the temperature after conversion (e.g., Celsius) be provided in a function call. In response to this function call, the server that provides the web service would return a number that represents the converted temperature. The function calls and responses are typically just XML calls that could actually be formatted by hand and sent back and forth.

A great deal of attention has been paid to the tools and definitions of the server-side components involved in web services, i.e., how to publish the server-side functions, how to make the web services available to be discovered and to be invoked, and how to support the incoming XML SOAP request and transform it into the native server-side programming environment where the execution of the service occurs. What has not been addressed, however, is a model to allow the service provider to create a client-side package that invokes the SOAP request.

This is important because, while the web services model gives a user the means to access web services, the user still has to figure out exactly how to implement these means (i.e., how to make the function calls). In a normal web services call, the client has to create the code to make the call, has to understand the semantics of the call's parameters (what does “address” mean”, how is it formatted, etc.). All of this is outside the scope of the information stored in the UDDI server. Thus, while the user may know that it is necessary to provide a value such as a date as one of the parameters of the function call, the particular format of the date in the function call may be unknown. Then, the client receives only “bare-bones” information returned by the server in response to the call. There is no formatting, control, or the like. Because the web services model focuses on the simple transfer of information back and forth through XML calls, there is no mechanism for the service provider to control the manner in which the services are presented to an end user. There is therefore no means to ensure, for example, that appropriate branding is used with the services.

These issues result in many of the interoperability problems that are conventionally experienced when using web services. Simply formatting an expression in XML doesn't solve these problems—it is still necessary to know what has to be accomplished and how it has to be done.

The result of these issues is that incorporating a web service in a site presents a whole host of problems. For example, suppose web site 200 (OnlineBank.com) wishes to integrate the web service provided by second web site 240 (TravelersChecks.com) in a manner in which the web services of TravelersChecks.com may be provided without having to leave the original OnlineBank.com site. In this case, the OnlineBank.com site will have to obtain a list of web services available from TravelersChecks.com, determine the web service it wishes to incorporate, determine what information is required by that web service, and construct an interface to obtain the required information from user 220 of the web site 200 (possibly using wizard 210). Once information is obtained from user 220, the site 200 (possibly using wizard 210) can construct a call to the web service (or transaction system 230) and return the results to user 220 of original web site 200. This is problematic, if the web service changes so must the interface for obtaining information from user 220, and the associated call to the web service, essentially breaking the original web site 200 (or wizard 210). Additionally, as the web service interface is presented by the OnlineBank.com site, the actual provider of the web service, TravelersChecks.com, has no way to control how its web service, or the results, are presented.

The embodiments of the present invention address the client side of the web services model by essentially allowing the client-side experience to be presented as the provider of the web service wants it to be expressed. This may include parameterization as appropriate to allow the experience to fit within the environment of the user of the web services, or a web site which incorporates the web service. This tool gives the web service provider control over the client-side expression of the web service and thus provides an ability to, for example, protect the brand associated with the service.

Referring to FIG. 5, one embodiment of the invention comprises providing a package 320 from a web service provider 310 to a web site which wishes to incorporate a web service, where package 320 contains a function call 321 corresponding to a particular web service, as well as some additional information or code 322 that can reduce the site's effort in attempting to make the function call to obtain the web service. Package 320 may therefore include one or more of the input, output or return parameters. Package 320 may also include code (e.g., in Java) that performs various functions, such as assisting the incorporating web site 200 in providing the appropriate function call parameters, actually making the function call to the service provider's transaction system, presenting the results of the function call to a user at a client, and so on.

By providing the incorporating web site 300 with function call 321 that is packaged in this manner, this embodiment of the invention gives the service provider some control over how the web service is being provided. The package provided to the site 300 provides enough information for the site 300 to be able to make a function call to web service provider 310 without having to struggle with the semantics, and also allows the service provider to retain branding associated with the service, as well as some degree of management control.

Thus, in the OnlineBank.com example used above, TravelersCheck.com would provide a packaged function call to OnlineBank.com. The package might contain some of the required input/output parameters, or might provide information to OnlineBank.com in order to enable the OnlineBank.com site to properly format the input/output parameters. This package can be comprised of text files in the form of HTML, XML or JavaScript that are deployed by the client to expose the Web Service in their environment. In addition, the packaged may be composed of an archive file (such as ear, tar, jar, war) containing compiled code from Java, C#, C++, etc. or a combination thereof including documentation. A properties file or style sheet or configuration file could be a way for the client organization to modify the behavior of the package to make any user interface or other components of the package fit into their application. Using this information, the OnlineBank.com site may obtain appropriate information from a user who whishes to utilize the web service.

Based on this information, OnlineBank.com may then make a function call to the web service provided by TravelersChecks.com. The package might also include Java code to make the call. The call itself and the result of the call (the service) would still be communicated between OnlineBank.com and TravelersChecks.com in the form of SOAP. Once OnlineBank.com receives these results from TravelersChecks.com they may be formatted according to information 322 in package 320, thus the results would be displayed to the OnlineBank.com user in a manner that conforms to the requirements of TravelersChecks.com. For instance, the results could be displayed with a TravelersChecks.com icon and/or using a trademark associated with traveler's checks provided by TravelersChecks.com. All of this functionality provided by the packaged function call could, for example, be wrapped up in a wizard of the type illustrated in FIG. 4.

It should be noted that the control of the function call and/or its results provided by the embodiment of the invention described above may nevertheless allow an incorporating web site to customize the package to fit within the site's own scheme. The site may therefore be able to modify the package (within the constraints of the service provider's controls) and distribute the modified package to its own affiliates, so that they can use the same package to obtain the corresponding service.

When a user wants to use the Web service, the package is activated. This may be accomplished by making a call to the Java code within the package, which then initiates the function call to obtain the web service. The information included in the package can control how to make the call, how to handle the confirmation, how to display the results of the web service to the user (e.g., how logos are displayed and what colors are used), and so on.

Those of ordinary skill in the art will understand that these methodologies for incorporating web services may be applied at any level. For example, packages for web services may be distributed directly to a user, or may be re-distributed by an incorporating web site to other web sites which wish to incorporate the original web service.

Those of skill in the art will also understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof. The information and signals may be communicated between components of the disclosed systems using any suitable transport media, including wires, metallic traces, vias, optical fibers, and the like.

Those of skill will further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Those of skill in the art may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

The various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with general purpose processors, digital signal processors (DSPs) or other logic devices, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), discrete gates or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be any conventional processor, controller, microcontroller, state machine or the like. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The steps of the methods or algorithms described in connection with the embodiments disclosed herein may be embodied directly in hardware, in software or firmware modules executed by a processor, or in a combination thereof. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

The benefits and advantages which may be provided by the present invention have been described above with regard to specific embodiments. These benefits and advantages, and any elements or limitations that may cause them to occur or to become more pronounced are not to be construed as critical, required, or essential features of any or all of the claims. As used herein, the terms ‘comprises,’ ‘comprising,’ or any other variations thereof, are intended to be interpreted as non-exclusively including the elements or limitations which follow those terms. Accordingly, a system, method, or other embodiment that comprises a set of elements is not limited to only those elements, and may include other elements not expressly listed or inherent to the claimed embodiment.

While the present invention has been described with reference to particular embodiments, it should be understood that the embodiments are illustrative and that the scope of the invention is not limited to these embodiments. Many variations, modifications, additions and improvements to the embodiments described above are possible. It is contemplated that these variations, modifications, additions and improvements fall within the scope of the invention as detailed within the following claims. 

1. A method, comprising: at a web service provider computer, creating a package containing: a function call corresponding to a web service; branding information associated with the web service; and code associated with the function call; and providing the package to a client computer, wherein the code assists a client web site in: making the function call to the web service running on a server computer remote from the client computer; and presenting results of the function call through the client web site with the branding information associated with the web service, thereby retaining branding associated with the web service provided through the client web site.
 2. The method according to claim 1, wherein the code assists the client web site in providing one or more function call parameters.
 3. The method according to claim 1, wherein the package includes information that enables the client web site to properly format input/output parameters required by the function call.
 4. The method according to claim 1, wherein the package includes text files for incorporating the web service in the client web site.
 5. The method according to claim 1, wherein the package includes a properties file, a style sheet, or a configuration file for client-side modification of the package.
 6. The method according to claim 1, wherein the package is redistributed by the client web site to one or more web sites for incorporating the web service in the one or more web sites.
 7. The method according to claim 1, wherein the client computer is associated with a user of the client web site and wherein the package is directly distributed to the client computer.
 8. A system, comprising: a processor; one or more non-transitory computer readable media storing instructions translatable by the processor to perform: creating a package containing: a function call corresponding to a web service; branding information associated with the web service; and code associated with the function call, wherein the package is provided to a client computer communicatively coupled to the system over a network, wherein the code assists a client web site in: making the function call to the web service running on a server computer remote from the client computer; and presenting results of the function call through the client web site with the branding information associated with the web service, thereby retaining branding associated with the web service provided through the client web site.
 9. The system of claim 8, wherein the code assists the client web site in providing one or more function call parameters.
 10. The system of claim 8, wherein the package includes information that enables the client web site to properly format input/output parameters required by the function call.
 11. The system of claim 8, wherein the package includes text files for incorporating the web service in the client web site.
 12. The system of claim 8, wherein the package includes a properties file, a style sheet, or a configuration file for client-side modification of the package.
 13. The system of claim 8, wherein the package is redistributed by the client web site to one or more web sites for incorporating the web service in the one or more web sites.
 14. The system of claim 8, wherein the client computer is associated with a user of the client web site and wherein the package is directly distributed to the client computer.
 15. A computer program product comprising one or more non-transitory computer readable media storing instructions translatable by the processor to perform: creating a package containing: a function call corresponding to a web service; branding information associated with the web service; and code associated with the function call, wherein the package is provided to a client computer associated with a client web site, wherein the code assists the client web site in: making the function call to the web service running on a server computer remote from the client computer; and presenting results of the function call through the client web site with the branding information associated with the web service, thereby retaining branding associated with the web service provided through the client web site.
 16. The computer program product of claim 15, wherein the code assists the client web site in providing one or more function call parameters.
 17. The computer program product of claim 15, wherein the package includes information that enables the client web site to properly format input/output parameters required by the function call.
 18. The computer program product of claim 15, wherein the package includes text files for incorporating the web service in the client web site.
 19. The computer program product of claim 15, wherein the package includes a properties file, a style sheet, or a configuration file for client-side modification of the package.
 20. The computer program product of claim 15, wherein the package is redistributed by the client web site to one or more web sites for incorporating the web service in the one or more web sites. 